Minutes, IBIS Quality Committee

20 January 2015

11:00-12:00 EST (08:00-09:00 PST)

ROLL CALL

Ericsson:                           Anders Ekholm
Intel:                              Michael Mirmak
IO Methodology                    * Lance Wang
Signal Integrity Software         * Mike LaBonte
Teraspeed Labs:                   * Bob Ross

Everyone in attendance marked by *

NOTE: "AR" = Action Required.

-----------------------MINUTES ---------------------------
Mike LaBonte conducted the meeting.

Call for opens and IBIS related patent disclosures:

- None

Opens:

- None

ARs:

- Mike draft IQ presentation for DesignCon summit
  - Done
  - This has been submitted for review.

- Mike recover percent format specifications in spreadsheet.
  - No new progress, but almost done.

- Mike add comments to CMPNT, DLY, MSPEC sections.
  - No new progress.

- Lance add comments to EBD section.
  - A spreadsheet was sent today.

- Bob add comments to CIRCUIT section.
  - No new progress.


Summit presentation:

- Mike showed the summit presentation.
- We did a quick review.
- Lance: Is 10% threshold for E1503 correct?
- Mike: The source code shows it is 10%.
  - The W1503 threshold is 2%
  - This may be controversial, the IBIS spec does not have a requirement.
- Lance: Even if there is a warning, the model could already be wrong.
- Bob: Mike is the one who pushed for those checks.
  - David Banas wants to use AMI models that do not comply.
- Mike: AMI models should not have V-T curves.
- Lance: That would be a good discussion to have.


IBISCHK Specification:

- Bob showed the 2005 Parser Spec document from Michael Mirmak.
- Bob: This has notes on the checks.
- Mike: That looks like just the message lines.
  - It uses 'xxx' whereas our spec uses variable names.
- Bob: This was written for IBISCHK4.
- Mike: This gives the exact source code version, we should do likewise.
  - The wip1 User Guide gives its version as 6.0.0.
  - The User Guide may not change each time the source changes.
  - We decided long ago to avoid having User Guide numbering that mismatches the source.
- Bob: We could have bug fixes that do not change intended functionality.
- Mike: Each time we post new ibischk executables we move the previous to an old_* directory.
  - The user guide should move with it but be copied to the top directory.
  - We might have to change only the version in it, but that's OK.

- Mike: It is not easy to determine which comments in our section files have been updated.
  - The estimate in our summit presentation that we have updated 50 comments is just approximate.
  - For example some spreadsheets use a color code that is not defined.
- Bob: We might use some checkin/checkout facility.
- Mike: It would be hard to formalize our process since the section files come back in different formats.
  - This might become awkward once we have all sections done.
  - The full length spreadsheet probably should be updated incrementally.
  - A safe approach would be to ask section authors to check the incremental updates.

Meeting ended: 12:03

Next meeting February 3